fix(postgres): Use with_bind_ports for postgres container #853
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
with_exposed_ports for ports != 5432 breaks -- the internal port is always 5432, we're just binding to different host ports.
hannah-heywa
changed the title
|
what are you trying to do and what is happening instead? testcontainers generates a random port - this behavior is ideal for tests, so that you can run tests in parallel, or even you can run the tests on a system where postgres is running on the default port (a random port wont conflict). that is the intended behavior. if you can share some details about what you are doing, i can help you figure out how to use testcontainers in your workflow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
with_exposed_ports for ports != 5432 breaks -- the internal port is always 5432, we're just binding to different host ports.